Skip to main content
CIECA Products

Implementation Guide - Indicating a Possible or Potential Total Loss

This implementation Guide is focused examples of populating <LossInfo> aggregate to indicate total loss. 

This is not a full data representation of the vehicle damage assignment request.

Data Dictionary Reference(s)

Assignment

Section 4 

Section 4.1 - Common Data Aggregates for Assignment
Section 4.2 - Assignment Add Request

Common Elements and Aggregates

Section 3


The hyperlinks in the Type Colum will help you navigate to the Aggregates and messages.  


<ctrl> click on hyperlink will take you to the Aggregate

<alt> and back arrow will take you back to hyperlink

Data Dictionary Help

Section 2


Describes the architecture behind the schemas.  This includes definitions, data types, building blocks, naming conventions, and versioning.

Test Instance(s)
  
AssignmentAddRequest_VehicleDamage_IG.xml    

Data Recommendations

Aggregate  Aggregate or Element Usage
 <ClaimInfo>Required if aggregates <orderInfo> or <FleetInfo>is not populated.  This example is for showing a possible Total Loss, so this aggregate will be populated.
 <ClaimNum>Recommended
 <ClaimInfot> / <LossInfo>
Recommended 

 <TotalLossInd>Recommended; 'Y' indicates damage is declared a total loss; 'N' indicates damage is not declared a total loss and 'U' indicates total loss status is unknown.  This example we will use 'Y' to indicate a Total Loss.

Master Code List

Code List are identified in the Type Column with Open Enum or Closed Enum in the Data Dictionary.  For a list of all the codes, please use the Data Dictionary and the Master Code List.

 Code List ValueDescription
No Code List used in this Implementation Guide